Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade base packages #169

Merged
merged 1 commit into from
Dec 18, 2017
Merged

Upgrade base packages #169

merged 1 commit into from
Dec 18, 2017

Conversation

yuvipanda
Copy link
Collaborator

  • Bump JupyterLab to latest
  • Run freeze.py (conda) and freeze.bash (venv) to get new dependent
    packages, primarily newer ipykernel and ipywidgets
  • Remove some over-specification in environment.yml

Fixes jupyterlab/jupyterlab#3240

- Bump JupyterLab to latest
- Run freeze.py (conda) and freeze.bash (venv) to get new dependent
  packages, primarily newer ipykernel and ipywidgets
- Remove some over-specification in environment.yml
@blink1073
Copy link
Contributor

@yuvipanda, I can make a note in the JupyterLab release notes, but it would help if there were some upgrade notes here to point to for which files to update and which scripts to run to make a PR.

@minrk minrk merged commit 1c7bd6e into jupyterhub:master Dec 18, 2017
@minrk
Copy link
Member

minrk commented Dec 18, 2017

Deployment has begun. I don't plan to bump the image prefix for this, which means any repos built before the deploy will still be considered valid with the previous version. This should be true in general: if a repo wants to ensure a particular version of jupyterlab/ipython/etc., it must specify that in its dependencies.

markmo pushed a commit to markmo/repo2docker that referenced this pull request Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants